docs: clarify OTLP HTTP client runtime compatibility#3513
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3513 +/- ##
=====================================
Coverage 82.8% 82.8%
=====================================
Files 130 130
Lines 27289 27289
=====================================
Hits 22622 22622
Misses 4667 4667 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
cijothomas
reviewed
May 11, 2026
TommyCpp
approved these changes
May 12, 2026
scottgerring
force-pushed
the
sgg/runtime-docs
branch
from
9f204f9 to
b54b99d
Compare
scottgerring
force-pushed
the
sgg/runtime-docs
branch
from
b54b99d to
650ac18
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We have a bunch of HTTP client features and some unintuitive rules around their usage; this PR tries to make the rules explicit.
I think long run we can probably do better than this but as we've had some feedback on this I think we should make it clearer immediately.
The advice is:
reqwest-blocking-client- this is the default behaviour with the stable processors. The async clients should not be used here.experimental_async_runtime? Usereqwest-client, orhyper-client